Reusing Application Artifacts |
|
Before you begin this task:
Ensure that the application containing the artifact you want to reuse is installed, and you have the required permissions to access it.
Process Platform provides a rich development environment to design integrated applications that contain user interfaces, business processes, roles, and so on. While developing such applications, you often need to reuse application artifacts deployed as part of other applications (developed by others or even by yourself). To reuse such application artifacts, you need to create a run-time reference in your project. The run-time reference can then be used as a regular design-time document.
Run-time references introduce dependencies on the applications that provide the referenced artifacts. Therefore, to be able to deploy your application, the referenced artifacts must be deployed first.
The following types of application artifacts are available for reuse once deployed:
Document |
Description |
|---|---|
|
Add a run-time Action Template reference, to use it in Rules |
|
Add a run-time Application Connector reference to use it for a Web Service |
|
Add a run-time Business Calendar reference, to use its data in a Business Process Model |
|
Add a run-time Business Identifier reference, to use it for identification of process instances in the Process Instance Manager. |
|
Add a run-time Business Measure reference to use it as data source for creating KPIs or in a User Interface for performance visualization in dashboards |
|
Add a run-time Business Process Model reference, to use it directly or to use it in a Business Process Model |
|
Add a run-time Case Model reference to manage cases in a Business Process Model |
|
Add a run-time Composite Control reference for use in a User Interface |
|
Add a run-time Condition Template reference to use it in Rules |
|
Add a run-time Content Map to be used in a Data Transformation |
|
Add a run-time KPI reference to reuse the indicators in the dashboards |
|
Add a run-time Decision Table reference to your business process model to reuse the Rules |
|
Add a run-time Organization Unit reference, to use it for creating an Organization Model |
|
Add a run-time Process Monitoring Object reference to use it as a data source in a Business Measure |
|
Add a run-time Role reference to reuse it in your Business Process Model |
|
Add a run-time User Interface reference to use it in a Business Process Model |
|
Add a run-time Web service interface to reuse the Web Services. We will get run-time Web Services and also XML schema run-time documents in the schema folder. |
|
Add a run-time Worklist reference to associate all the worklist tasks to your business process model and your Inbox |
(Action Template)
(Application Connector)
(Business Calendar)
(Business Identifier)
(Business Measure)
(Business Process Model)
(Case Model)
(Composite Control)
(Condition Template)
(Content Map)
(KPI)
(Decision Table)
(Organization Unit)
(Process Monitoring Object)
(Runtime Role)
(User Interface)
(Web service Interface)
(Worklist)This option facilitates reusing existing run-time content instead of recreating the same content at design-time.
- In the Workspace Documents (Explorer), open <solution>, right-click <project> or <folder> and select Add Runtime Reference > Other. The New Runtime Reference dialog box appears, displaying all the runtime documents.
- Select the document that you want to refer. A window pertaining to the selected document appears, displaying the run-time information containers.
- Browse through the containers and select the run-time document that you want to refer.
- Click Next. The next screen of the window appears with the details of the selected run-time document.
- Provide additional details in the Additional Instructions box to install the run-time reference, and click Finish. The window closes.
The run-time document is added to the existing project as a reference.
Note:
In team development scenarios, run-time references may be incorporated into your workspace without deploying the providing application on your development environment. In those cases, you can still build and package the enclosing projects. However, while publishing the project, for each run-time reference, the computer will check whether a compatible version of the referenced artifact is deployed. In case the referenced artifact is not available or when its interface contract has changed, publishing will fail.